Email Open Pixel Tracking Consent - Technical Guide for Data Processing and Reporting

Cheetah Digital now offers Open Pixel Tracking Consent for Email, a solution that lets marketers continue or turn off recipient-level email open tracking based on recipients’ consent preferences or their organization’s tracking policy.

Managing recipient consent for email open tracking helps you respect recipients’ privacy choices and support your organization’s compliance requirements.

This overview explains:

  • The data flow and technical behavior of Email Open Pixel Tracking Consent
  • Data retention for email open data when recipients are not tracked
  • Impact on reporting

For configuring this feature within your Cheetah Digital user interface, including recommendations and best practices, see Managing Consent for Email Open Pixel Tracking.

 

Content Guide

Section Coverage
End-to-End Process Overview of Consent handling, pixel execution, processing paths, and reporting end state
Anonymization Process Identifier inputs, hashing, regeneration anonymous ID
Data Retention Data disposition, storage, and retention
Deliverability & List Hygiene Last Open Date, Email Domain, permitted purpose, and current controls
Reporting & Aggregation Event processing, reporting context, and small-audience behavior

 

End-to-End Process Flow – Consent and No Consent Recipients

 

Processing sequence

  1. Message preparation: The platform checks the consent value during message list creation and adds the No Consent parameter for No Consent status before deployment begins.

  2. Email deployment: The original recipient ID remains intact at send time, allowing the platform to process the recipient’s Last Open Date when an open occurs.

  3. Pixel execution: When the open URL is executed, the recipient ID is temporarily processed in memory. The platform saves the Last Open Date and Email Domain information for deliverability and list-hygiene.

  4. Anonymization: The platform checks for the No Consent parameter. Where present, it then hashes/anonymizes the recipient ID associated with the open event. It saves the open engagement event but only with the anonymized ID to allow for aggregated reporting.

  5. Reporting: Events are subsequently summarized into aggregate data during report calculation. Deliverability items: Last Open Date remains on the identifiable recipient record. Domains are reported at aggregated level only.

 

Anonymization Details

Anonymization process overview

  1. During the campaign creation process after campaign launch a “no consent” (NC) identifier (parameter) is added to the URL for those recipients whose status is 1500 (no consent to track).

  2. When the campaign is sent, recipients are not yet anonymized, the unique recipient ID for each recipient is intact. This allows the platform to save the Last Open Date and the opens per Domain.

  3. When the recipient opens the email – first processing step, the platform records the Last Open Date and Domain for list-hygiene and deliverability purposes.

    Last Open Date

    • Can be used for deliverability and list-hygiene purposes
    • Saved for all recipients, consented or no consent
    • Retaining Last Open Date at the recipient level is necessary for it to be actionable for list-hygiene and engagement management, such as identifying recipients who have not opened an email within a defined period
    • Date of the most recent open is retained; each new open overwrites the previous Last Open Date
    • No open time or location is stored as part of this field.

    Domain

    • The recipient's email domain is retained to identify and address mailbox-provider/domain-level delivery issues
    • The platform already makes this available for all recipients
    • Domain opens are reported at aggregate level and not tied back to individual recipients.
  4. When the recipient opens the email – second processing step: the platform checks for the NC parameter in the URL and anonymizes the recipient ID for use for aggregate reporting. If NC is present:

    • The recipient ID associated with the email open-event is hashed/ anonymized
    • Hashing is irreversible and is therefore not a pseudonymous process which can be reversed
    • The anonymized open event is saved in our database and used for aggregate reporting where individual recipients cannot be identified.

 

Anonymization regeneration

The anonymized ID for No Consent recipients can be regenerated as needed to support measurement of Unique Opens without exposing the recipient's identity in reporting.

The anonymized ID is generated using three inputs: the recipient ID, the customer ID, and a secret key.

  • If the No Consent recipient opens the email multiple times, the same anonymized ID value is generated each time, using the same inputs
  • If the No Consent recipient opens another campaign, the same anonymized ID will be generated, once again, using the same inputs.

 

Recipient linkage and technical limitations to match regenerated anonymous ID

The platform retains the recipient ID, customer ID as part of recipient profile.

The anonymized open event does not retain the recipient ID, customer ID and secret key together to match and identify the recipient.

Data handling by element

Data element Disposition and storage Retained association
Original recipient ID Temporarily processed in memory for milliseconds to allow Last Open Date handling. This temporary value is not accessible to platform users. Links to recipient profile
Anonymized ID Retained as a hashed negative number in the platform database. Does not display on the platform. Links to open event and campaign ID for aggregate opens reporting
Open event Retained in the platform database Linked to anonymous ID
Last Open Date Retained in the platform database as a date without time. Is replaced with latest Last Open Date. Linked to the recipient record and recipient ID
Email domain Retained in the platform database Linked to the open event, aggregate reporting only
IP address Not saved.  No retained association
User agent or device information Retained in the platform database Linked to the anonymous ID
Campaign ID Retained in the platform database Linked to the anonymous ID for aggregate opens reporting

 

Deliverability & List Hygiene

Cheetah Digital retains the most recent Last Open Date and retains Email Domain information for all recipients regardless of consent value for deliverability and list-hygiene. These retained values serve different purposes and have different associations.

Last Open Date

  • Last Open Date is linked to the full recipient email address and individual recipient record through the recipient ID.
  • It contains the date of the most recent open event, without time or location.
  • Each new open replaces the previous date. The history of recipient opens is not retained. It is not linked to campaign information.

Usage

Keeping this date on the recipient record allows list hygiene actions, such as identifying recipients who have not opened an email within a defined period.

  • There are no controls in place governing marketers’ use of Last Open Date or preventing its use beyond deliverability and list-hygiene.
  • The field could be used to select audiences, retarget recipients, measure engagement, or optimize campaigns.
  • Last Open Date retention cannot currently be switched off independently of aggregate reporting. Further evaluation is required to determine whether to offer that option.
  • There is no dedicated deliverability-only pixel in the current solution.

Email domain

An email domain is the portion of an email address after the @ symbol, such as gmail.com. It identifies the receiving email provider or domain. The domain value is retained with the anonymized open event to support monitoring delivery performance and identifying issues across mailbox providers or domains.

There is no dedicated deliverability-only pixel in the current solution.

Reporting & Aggregation of Open Events

The platform collects individual engagement open events and then summarizes them for aggregate reporting.

  • For recipients with Consent: the usual recipient-level tracking and aggregate reporting path remains available
  • For recipients with No Consent: open events use an anonymous ID and are available in aggregate reporting only
  • Recipients with no consent cannot be identified in segmentation or exports reports for opens
  • Deliverability Metrics: Last Open Date remains on the identifiable recipient record. Domains are reported at aggregated level only.

Small audiences and inference

  • The platform does not apply a minimum-recipient threshold before displaying aggregate campaign reporting.
  • A segment with one recipient is processed the same as a larger dataset.
  • The platform does not currently offer suppression below a defined audience size or controls against repeated or cross-sliced reporting queries.
  • Introducing minimum-audience controls is not currently planned.

Example: If a campaign was sent to one person and the report shows an open, it may infer that person’s behavior.